home *** CD-ROM | disk | FTP | other *** search
Text File | 1998-01-31 | 3.1 KB | 88 lines | [TEXT/ttxt] |
- PictViewer version
-
-
- Version history
- ---------------
- version 0.0 1995 private personal eyes only non-release
- version 1.0 1997 hurried public release. Beware!
- version 1.1 1998 what 1.0 should hve been (and would have been if I had had the time)
-
-
- Improvements from version 1.0
- -----------------------------
-
- * support for newer PICT opcodes (notably 32 and 16 bits color images)
- * PowerPC native where available (FAT)
- * open PICT files
- * fixed many large and repulsive bugs
- * stopped the largest memory leaks
- * fixed scrolling
- * many other small improvements
-
-
- What it does
- -------------
- PictViewer disassembles Macintosh pictures (PICTs). Macintosh PICts consist of a series of
- operation codes (opcodes), each followed by a variable amount of data. For a reactangle, for
- instance, the entry in the picture code consists of the opcode for a a rectangle followed by
- the four coordinates of the rectangle.
- PictViewer parses the picture code and displays each drawing operation as one line of text.
- Large data structures (pixmaps, for example) are abbreviated. It also handles most of the
- 'standard' picture comments.
-
-
- What is does not do
- -------------------
- There are a number of items on the to do list, such as printing, and picture editing, more
- elaborate display of data (headers, postscript comments etc.). Since my time is very limited,
- don't count on a new version for a very long time (unless I lose my job ;-).
-
-
- Instructions
- ------------
- Just open a PICT file or open a new window and paste your PICTure to view the dissassembled
- PICT code.
-
-
- Technical info
- --------------
- The most obvious way to disassemble a PICT on a Mac is to spool the picture to a port
- and catch the operations in the QuickDraw bottleneck routines. The advantage of this method
- is that it is easy to implement and will be compatible with future versions of the system
- software. PictViewer takes a different approach: it parses the PICT opcodes manually. This
- gives more detailed information, but it is also tricky: Apple reserves the right to change
- the opcodes. This would break PictViewer while the other method would still work.
-
-
- Why did you write it?
- ---------------------
- I'm glad you ask. This is a program I've written primarily for myself. This means that it
- is not very well tested. I've used it to check how applications handled pictures (and
- especially picture comments). This is handy if you're trying to write an application that
- generates pictures with smooth curves, thin lines etc. and wants to print them correctly.
-
-
- What does it cost?
- ------------------
- Zip! Nada! etcetera.
- Yep, it's free. Just don't distribute it for a fee or without this document.
- Also, I do not claim this program is fit for any use and I cannopt, therefore, be held
- responsible for any damage that occurs through the use of this software. You know the kind
- of legal bull.
-
-
- Known bugs
- ----------
- * very long pictures (with many lines of disassembly) will not be shown in full in the PictViewer
- window. The solution is to save the disassembly nin a file and view it in your favorite text
- editor (the adjective excludes SimpleText).
-
-
- Comments
- --------
- Comments are welcome at
-
- b.f.tuinstra@stm.tudelft.nl
-
- ENJOY!
-